Proxy server collection of data for module incorporation into a container document

ABSTRACT

A proxy server system comprising a request input unit that receives a request to collect data from a target server, a target server collection unit that collects data from the target server and an output unit that transmits the data for use by a module to generate data for a container document.

FIELD OF THE INVENTION

Embodiments of the present invention relate to incorporating remotemodules into a container document.

BACKGROUND OF THE INVENTION

Many websites offer users the capability to personalize a homepage. Suchwebsites have typically offered the user the opportunity to includepredefined sections of information or data in a predefined presentationformat selected from choices designed and incorporated by the websiteoperator. The user of such systems typically may personalize the contentwithin the sections, such as selecting specific stocks to include in asection showing stock prices. These personalized pages provide verylimited flexibility.

This and other drawbacks exist with current systems.

SUMMARY OF THE INVENTION

Accordingly, various exemplary embodiments of the present inventions maybe directed to a proxy server system. The proxy server system maycomprise a request input unit that receives a request to collect datafrom a target server, a target server collection unit that collects datafrom the target server and an output unit that transmits the data foruse by a module to generate data for a container document.

Another exemplary embodiment comprises a system that may comprise acontainer server that serves a container document to a user with one ormore associated modules and a proxy server system that receives arequest to collect data from a target server, collects data from thetarget server and transmits the data for use by a module to generatedata for a container document.

Another exemplary embodiment may comprise a method for serving contentcomprising collecting data from a target server using an originatingaddress that proxies an address accepted by the target server andtransmitting the data from the target server to a server for use by amodule to generate data for a container document.

Another exemplary embodiment may comprise a method for deliveringcontent comprising transmitting a request for data from a target serverto a proxy server and receiving from the proxy server data that wasobtained from the target server.

Another exemplary embodiment may comprise a proxy server system. Theproxy server system comprises a request input unit that receives arequest originated from a user browser upon opening the content of amodule included in a container document the browser is displaying, therequest specifying a target server from which to collect data, a targetserver collection unit that collects data from the target server and anoutput unit that transmits the data for use by the module to generatedata for the container document.

Other embodiments may be considered.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an overall system architecture according to variousembodiments of the present invention.

FIG. 2 depicts an illustrative container document according to anembodiment of the present invention.

FIG. 3 depicts an illustrative process for adding a module into acontainer document according to an embodiment of the present invention.

FIG. 4 depicts an illustrative interface for identifying a moduleaccording to an embodiment of the present invention.

FIG. 5 depicts an illustrative module specification format according toan embodiment of the present invention.

FIG. 6 depicts an example of data containing a module specificationaccording to an embodiment of the present invention.

FIG. 6(b) depicts an example of data containing an altered modulespecification according to an embodiment of the present invention.

FIG. 7 depicts an illustrative process for incorporating data from amodule into a container document according to an embodiment of thepresent invention.

FIG. 8 depicts an illustrative process for generating data from a moduleaccording to an embodiment of the present invention.

FIG. 9 depicts an illustrative process for enabling a module to beinlined in a container document according to an embodiment of thepresent invention.

FIG. 10 depicts an illustrative listing of the types of preferenceinformation that may be stored according to an embodiment of the presentinvention.

FIG. 11 depicts an illustrative system architecture according to anembodiment of the present invention.

FIG. 12 depicts an illustrative process for delivering target serverdata from a module to a container document according to an embodiment ofthe present invention.

FIG. 13 depicts an illustrative container document containing moduleswith output generated through a proxy server module according to anembodiment of the present invention.

FIG. 14 depicts an illustrative embodiment of a third party web siteincorporating a module through syndication with an advertisementincluded therewith according to an embodiment of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENT(S)

Exemplary embodiments of the invention are discussed in detail below.While specific exemplary embodiments are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfiguration can be used without departing from the spirit and scope ofthe invention.

A personalized portal site (e.g. My Yahoo!, start.com, or GooglePersonalized Homepage) may allow the user to select only content (e.g.,interactive, read-only, updating, data feeds, etc.) to display on apersonalized page, such as a new email alerts, current weather and/ortraffic conditions, movie showtimes, horoscopes, etc. According to oneembodiment of the present invention, these various modules that may beincorporated into a personalized portal page (one example of a containerdocument) along with modules developed (e.g., by an a third partydeveloper) for inclusion in the container.

Various embodiments provide a protocol for communication between ahosting site (e.g., container server system) and a module server (e.g.,one operated by an entity other than the user or the hosting site),process instructions that describe the functionality of a module(wherever hosted), a structured repository system for module data andcode that may include fixed module data and code as well as per-userconfiguration information or user preferences (e.g., in a weathermapping module, the postal codes in which the user is interested), and aproxy system that enables use of target site data in a site.

The system may comprise a number of components. The system may comprisea container server that serves a container document (e.g., apersonalized page). The container document “contains” one or moremodules, including one or more remote modules. As used herein, the term“container document” or “container” should be understood to include apersonalized homepage of a website, a sidebar, toolbar element thatincorporates one or more such modules, a page hosted by a site, adocument capable of rendering modules (e.g., any document capable ofrendering HTML code or XML code) in the format of the module (e.g.,XML). Also, the container may be a website of another entity thatincorporates the modules when supplied the modules through a syndicationsystem.

As used herein, the term “module” may be understood to refer to a pieceof software and/or hardware that renders data for use in a containerdocument. Modules may be personalized to user preferences, preferencesof the container, preferences of the environment or other inputs. Amodule specification may be understood to include a set of instructionsused to render data for the container document using elements that havebeen predefined.

Overview and System Architecture

FIG. 1 depicts an overall system diagram according to one embodiment ofthe present invention. As illustrated, FIG. 1 may comprise a host serversystem 10 with a plurality of modules that may be associated therewith.Such modules may comprise a container server 12, a module server 14, aspecification server 16, a back end server 18, an analysis module 28, amodule creation server 32, a syndication server 34, an advertisementserver 36, a geocode server 37 and a map server 39. As illustrated,personalized container server 10 may connect over a network 26 to aplurality of systems.

Other systems connected to the network may comprise one or more usersystems 22, one or more remote source systems 24, one or more moduledeveloper systems 30 and one or more syndication recipient servers 38.In addition, one or more database systems 20 may operate in conjunctionwith the various modules of host server system 10.

Container server 12 may serve the container document to user systems 22over network 26. Container server 12 may comprise a web server orrelated server systems that takes data and/or instructions andformulates a container for transmission over the network to the usersystem 22. It should be appreciated, however, that container server 12may reside on user system 22 as well so that a network connection maynot be used. In the example in which the container document comprises aword processing document, for example, container server 12 may comprisea word processing module.

Module server 14 may provide data from modules to container server 12for incorporation into a container document. It should be appreciatedthat in one embodiment, container server 12 and module server 14 maycomprise a single unit performing both functions. Module server 14 mayprovide data for the container document by interpreting and/or parsinginstructions in the module specification associated with the module.According to one embodiment, module server 14 may serve the modulecontent to the container document through the use of a browser IFRAME.An IFRAME may be generally understood to be an independently operatedbrowser window instance inside the container document. One advantage ofan IFRAME is that is protects the container document from the IFRAME'scontent and vice versa, e.g., JavaScript on the container document maynot be permitted to access any JavaScript code in the inner IFRAME (samefor CSS, DOM, or cookie objects).

To expedite display of container documents, modules may be displayedinline within the container document. Inline display may be understoodas referring to display with other document elements. One example is adisplay generated from code for HTML in the body according to HTMLstandards. In one embodiment, module server 14 or some other componentmay determine whether the module is deemed trusted prior to including itin the container document inline due to the risks of various securityissues an inline module could create. According to one embodiment, themodule may incorporate an indicia of approval (e.g., digitalcertificate) issued by the container module or an entity associated withthe container module as described in detail below. If the indicial ofapproval is present, module server 14 may render the data from a modulefor inline presentation in the container document.

Specification server 16 provides the module specification file to moduleserver 14. The module specification may be cached and stored in adatabase accessible to the module server 14 and/or specification server16 or may be retrieved from a location associated with the specificationas detailed later. For example, specification server 16 may reside on aremote source system 24. In addition, specification server 16 may beconnected to module server over a network with the module specificationlocated at another location on the network accessible to specificationserver 16.

Backend server 18 may be provided for interacting with one or moredatabases (e.g., large or dynamic databases of information). Forexample, for a news module that obtains frequent updates and demands aflow of data, (e.g, from an RSS feed), backend server 18 may format thedata into HTML for the container.

In one specific example, a person may create a module (e.g., a mapsmodule), such as one that uses an application program interface (API) toan existing mapping program to create a module to display a map ofdowntown Mountain View, Calif. The module may comprise an XMLspecification file or module specification file stored on aspecification server. The specification server may comprise any server,including one on the site from which the container page is hosted or anyother site. The user or another person may then include this new moduleon a personalized homepage (container document). The server that servesthe container document may operate as the module server and the serverthat generates the mapping data through an inquiry from its API may beconsidered to be the backend server.

According to one embodiment of the present invention, analysis module 28may analyze modules at various times (e.g., when the module is firstselected by a user, each time the module is called by a container forinclusion or at any other time determined to be advantageous for safetyand security and other times). Analysis module 28 may perform a numberof actions, including comparing the module with a list of disapproved ordangerous modules or a list of approved modules. The comparison mayinvolve exact or substring (e.g., prefixes, suffixes and regularexpressions) matching by name or location (e.g., URL), contents of thespecification, contents of the location where the specification resides,or information that may be ascertainable about the module. Analysismodule 28 may take one or more actions in response to a determinationthat the module is disapproved or dangerous, including, for example,silently blocking the request, (i.e. providing a generic error),blocking the request with an error that explains the reason it wasblocked or redirecting the request to a different module specificationthat has been determined to be safe and related to the disapprovedmodule (e.g., another module that relates to maps, if the first one wasa disapproved mapping site or a module that includes the keyword“basketball” if the disapproved module was a basketball module). Forexample, through redirection, the URL of the original module may bepassed to the “safe” module. The safe module may then use a proxyserver, as described below, to retrieve the original URL's content.Developers may then replace the error handler to fix small bugs in theoriginal module to be able to display the content of the originalmodule. In another embodiment, analysis module 28 may parse the modulecontent to determine whether it is safe, such as by compiling JavaScriptor other scripts contained in the module to try to identify unsafe orundesired actions the module may perform.

One or more module creation servers 32 may be provided. This server mayoperate as a “wizard” to enable module creators to create a modulethrough an interactive process controlled by module creation server 32.For example, module creation server 32 may provide a series of userinterfaces that enable the module creator to provide inputs that arethen used by the module creator to automatically generate a modulespecification. For example, various module specification templates maybe provided with corresponding inputs. Module creation server 32 maythen take inputs supplied by a module creator, insert them into thetemplate and then generate the module specification for the module. Apreview, testing and debugging function may also be offered as part ofthis “wizard.” This module may be downloadable as well so it may beinstalled and operated at any node on the network.

A syndication server 34 may prepare data for transmission to one or moresyndication recipient servers 38 related to modules. Syndication server34 may receive a request for a module and/or module content and deliverthat module or content to a syndication recipient server 38 over network26. Syndication server 34 may reside at host server system 10 or atanother location on the network. For example, if an operator of a sportsweb site (an example of a syndication recipient system 38) desired toinclude a maps module created by a remote source system 24, it may do sothrough a request to syndication server 34. Syndication server 34 maythen cooperate with module server 14 to generate data for the containerdocument (here the sports web site page of the syndication recipientsystem 38). That may involve retrieving the module specification fromremote source system 24, supplying preferences received from thesyndication recipient server 38 (e.g., city information for the sportsteam of a page being displayed) and/or generating data for thecontainer. It is also possible that the data may be rendered atsyndication recipient server 38 into its container document in either anIFRAME or inline. Syndication server 34 may thus syndicate modulesaccessible to it. It may do so based on requests for specific modules orother criteria it determines (e.g., content matches, keyword matches,monetary values associated with modules and/or syndication requestors,etc.)

Ad server 36 may provide advertisements associated with modules tocontainers. For example, an advertisement may be incorporated withmodule data when data is delivered to a container document. Ad server 36may operate with syndication server 34 to deliver advertisements tosyndication recipient servers 38 based on a syndication request for amodule. The advertisements may be selected by ad server 36 based on awide variety of criteria, including, but not limited to, therelationship between the content of or information about the container,module, other modules in the container, syndication recipient serverinformation, monetary elements/relationships related to any of theforegoing and/or combinations thereof. Ad server 36 may comprise theGoogle AdSense system, according to one embodiment of the presentinvention. Ad server 36 may operate as described in one or more of thefollowing patent applications, the subject matter of which is herebyincorporated by reference in their entirety. Specifically, ad server 36may manage online advertising by associating two or more conceptsrelated to a module with an advertisement and associating a bid,collectively, with the two or more keywords in the manner discussed inthe context of serving advertisements with electronic documents in U.S.patent application Ser. No. 10/340,193, filed on Jan. 10, 2003, entitled“Pricing Across Keywords Associated with One or More Advertisements,”which is incorporated by reference herein in its entirety. Additionalexamples of presenting advertisements and managing advertising costs arediscussed in U.S. patent application Ser. No. 10/340,543, filed on Jan.10, 2003, entitled “Automated Price Maintenance for Use With a System inwhich Advertisements are Rendered with Relative Preferences” and U.S.patent application Ser. No. 10/340,542, filed Jan. 10, 2003, entitled“Automated Price Maintenance for Use With a System in WhichAdvertisements are Rendered with Relative Preference Based onPerformance Information and Price Information,” which are incorporatedby reference herein in their entirety.

A geocode server 37 may be provided to generate geocode information fromlocation descriptions as is known in the art. A geocode server 37 maygenerate latitude and longitude numeric values from geographiclocations.

A map server 39 may generate map output. Mapping systems, such as GoogleMaps and Google Earth, may be used to generate this data.

One or more database systems 20 may be provided that store, in anynumber of ways, container information, module specifications and/orrelated information, formatting data, per-user and per-module preferencedata, remote module ID data, remote module location reference data,advertisement data, advertiser data, content/monetary data, syndicationrecipient data, templates for modules, inputs for modules, lists oftrusted and untrusted modules, approval criteria and related informationand/or any other information used by the modules to operate as describedherein. While a single database structure is shown, it is wellunderstood that the data may be stored at a number of locations and inone or more systems.

While one configuration is shown in FIG. 1, it should be appreciated byone of ordinary skill in the art that other configurations of thesevarious modules may also be possible. For example, the various modulesdepicted within host server system 10 may be disposed at variouslocations around network 26 or at various points on several networks. Inaddition, whereas a single host server system 10 is depicted, it shouldbe appreciated that any number of each of the modules depicted on FIG. 1may be provided including network 26.

In one embodiment, network 26 may comprise the Internet. Other networksmay also be utilized for connecting each of the various systems and/orservers.

In addition, what is shown as user system 22 may also operate as aremote source system 24 and/or a module developer system 30. In otherwords, one computer system may operate in different capacities: as auser system, as a remote source system, as a syndication server, as atarget content server, and/or a module developer system. In addition, asexplained in greater detail below, each of the modules depicted withinhost server system 10 may also be disposed at a user system 22, a remotesource system 24, or a module developer system 30. Similarly, databases20 may be associated with each of the modules depicted within FIG. 1depending upon the configuration desired.

Illustrative Container Document Including Modules

According to one embodiment of the present invention, systems and methodare provided to incorporate modules into a container document. Oneexample of a container document would be a personalized home page, suchas the Google Personalized Homepage currently available to users of theGoogle services on the Internet. Instead of restricting the types ofcontent that a user is able to include in a container document such as apersonalized home page, one or more embodiments of the present inventionenable users to select modules from sources other than the source of thecontainer document. So, for example, a user may elect to include amodule in his or her personalized Google home page from a source notassociated with Google.

It should be appreciated that various forms of the container documentmay exist but one such illustrative example is depicted in FIG. 2. FIG.2 depicts a container page 100 with a plurality of modules that havebeen incorporated into the container document. A plurality of methods ofincorporation are possible including the use of the IFRAME and inlineHTML techniques. These issues will be discussed in greater detail below.FIG. 2 depicts a plurality of modules including a photo remote module101, a task list module 102, a game module 104, a stock module 105, amaps module 106, a remote module 108, a remote module 210, a remotemodule 312, and a remote module 114. Different formats for the variousmodules may exist depending upon the specifications provided by thecreator of the module. As depicted, some modules may provide scrollbars, and others may not. Some modules may be different sizes or shapesthan other modules. In addition, some modules may offer the opportunityfor the user to edit the display preferences and/or per-use dataassociated with the module. (See, for example, modules 102, 104, 105,106 and 110 that provide an edit link.) For example, if the modulerelates to a maps module 106, the user may be provided the opportunityto edit an address or addresses that are mapped in that module. In oneembodiment, inlined modules may be automatically sized by a containerdocument so no scrolling, height or scaling information may be provided.If a module developer wants the module to have these properties in thisembodiment, an inlined module may be wrapped with a fixed size <DIV> tagand content placed in the tag. The scroll bar, height and othercharacteristics may be then specified for the inlined content. One ofthe attributes allows specifying scaling=“ . . . ” to let the developerindicate how a module may be scaled up or down for different sizes ofplacements in the container documents.

One of the functions provided with this example container document 100is the opportunity to add content to the container page throughselecting the add content element 103. Upon selecting “add content”element 103, the system may offer the user the opportunity tointeractively indicate an additional element to be included in thecontainer page. Various forms of an interface to receive that input maybe provided. One illustrative form is presented in FIG. 2 toward thebottom of the page in section 120. In that section, the user may bepresented with an interface element to select from a browsable list ofmodules that may be arranged into a categorization structure. Anothersection of input section 120 may enable the user to specify a referenceto a location for a module to be incorporated into the containerdocument. Such a section may be such as that depicted through an inputbox 126 with a submit element 128. In one illustrative example, the usermay specify a location reference (e.g., the uniform resource locator(URL)) where data exists related to a module to be incorporated. Asexplained in greater detail below, one example of the data is anXML-based file that meets the scripting preferences of the operator ofthe container document system 10.

Another option is depicted in FIG. 4 wherein the user may interact withan interface that allows the user to browse through modules by categoryin section 402 with a plurality of indicated available modules insection 403 or for the user to utilize a search functionality 404 wherethe user may put in information into a search box 406, select the searchbutton 408 and have results displayed in section 410. The results ofthese searches and displays may provide the location reference (e.g.,URL) of data (e.g., an XML file) for use in incorporating the module andthe container document as described below with reference to FIG. 3 andother descriptions provided.

In FIG. 2 or 4, a preview of a module, author name, author affiliationand/or author email may be provided. To provide protection for email, ananonymized email forwarding feature may be used to help protect againstspammer-crawlers. The display may also provide information about what amodule requires or works best with using a May-Require attribute from amodule preference (as described in detail below). Here the module worksonly with the Firefox browser and so that information is provided.Locality information may also be provided. Here, this module is designedfor the Untied States and for English and Spanish.

In addition, in adding, editing or deleting modules, it may be desiredto have those activities occur without a refresh of the containerdocument. One illustrative technique for achieving this may involve useof AJAX so a module may be added to a container document without arefresh of the container document page (perhaps only a refresh of theIFRAME in which the new container is presented), or use of AJAX toremove a module without the container document being refreshed or when adeveloper is developing a module, being able to change modules withoutthe container document in which they are populated having to have a pagerefresh in order to incorporate the changed module.

FIG. 14 depicts another illustrative example of a container. Thiscontainer may be operated from a container server that is not affiliatedwith the module server. The container 1400 may be a third party website(here Joe's Real Estate Web Page) that lists real estate listinginformation. A remote module 1401 may be incorporated throughsyndication from a module server. Here, the remote module may comprise amortgage calculator that Joe's Real Estate Web Page may find useful forvisitors to its site. With the module, one of more advertisements 1403may also be provided, as illustrated.

Illustrative Methods

FIG. 3 depicts an example of a method 300 used to add a module to acontainer document. According to one embodiment, in block 302, acontainer document may be opened into which a new module is to be added.This may be performed by presenting the container document to a user orby a computer software element opening the container document todetermine its contents, for example. In block 304, a selection ofcontent to be added is received. This content selection may be receivedfrom a user such as through the inputs described with reference to FIG.2 or FIG. 4 or through some other mechanism by which the user mayprovide an indication of a module to be added to the container. Inaddition, in block 304 modules may be provided through an automatedprocess whereby the system determines a module to be added based uponvarious inputs.

In the case of a user input of, for example, a request to add contentthrough module 103 of container page 100, in block 308 it may bedetermined whether the user is requesting the addition of a modulethrough a list of available modules or through a reference. If the useris providing an input from a list, the content from a menu selection maybe received in block 310. That may be achieved by interaction of theuser with an interface such as that depicted in FIG. 2 or FIG. 4 byselecting one or more modules presented such as that in 124 or 403 forexample. Other methods of receiving a selection of a module may also beprovided. If the user is providing a selection of a module from areference, then in block 312, a location reference may be received. Tofacilitate the user's ability to identify the data for the module, anoptional block 313 and 315 may also be provided. In block 313, if theuser's remote location identifier ends with a slash, for example, orother indicator that the user is asking for files at the location to beretrieved, then in block 315, a list of possible modules may bedisplayed. Block 315 may involve taking the remote location identifierprovided by the user and querying that location for a listing of filesor data representing module specifications, and presenting the receivedresponse to that query in a list for the user to choose. For example,the user may be provided a list of files of module specifications at thelocation provided whereby the user may select in block 317 one of thosepresented files. For example, if the user provides a URL that ends in aslash or provides some other incomplete location reference, the systemmay in block 315 retrieve a listing of all files containing modulespecifications at the location of the URL whereby the user may chooseone of the files, such as one of the XML files in block 317. In anotherexample, the system may automatically guess from the content or providea directory listing or object listing (e.g., through a database query)using web server resources, such as an Apache webserver directory callor IIS directory call. The list may be formatted in a way to make iteasy to select such as by highlighting more likely choices.

In block 314, the system may optionally enable the user to confirm theselection of the module to be added before the container page isupdated. Upon performance of block 314 or if a confirmation action isnot included in the process, after blocks 310 and/or 312 and/or 317, anoptional approval block 318 may occur.

According to various embodiments of the present invention, the operatorof the container document may desire to protect the security of thecontainer as well as the security of the user systems interacting withthe container. Accordingly, one or more actions may be taken todetermine whether the module is approved prior to enabling the contentto be incorporated in the container. For example, an evaluation of thecontent may occur to determine whether a module is trustworthy, forexample if there are not HTML tags or other characteristics determinedto be trusted. These actions are described in greater detail below. Ifthe approval is not met, then in block 320, one or more unapprovedresponses may occur as described above with reference to analysis module28.

If approval occurs, in block 322, the updated container document may bepresented to the user or to whomever has provided the input of themodule to add to the container.

As described in greater detail below, according to the presentinvention, a specification may be provided for modules to utilize inorder to be incorporated into a container document by the host serversystem 10. FIG. 5 depicts a module specification according to oneembodiment of the present invention. At its base level, thespecification may comprise a plurality of elements including the XMLversion information, module preferences, which may be optional, userpreferences, which may be optional, a content type designator and then acontent element that is used to populate the portion of the containerallocated for the module. It should be appreciated that the content maybe specified in various forms of code, typically code that isinterpretable by a user system when generating the container forpresentation. Such code may include HTML, JavaScript, or other forms ofcode that may be used to depict the format of a web page.

According to another embodiment of the present invention, the modulespecification may be embedded in one or more other files or computerinstructions. According to this embodiment, the module server 14 may,when provided with the identification of data for generating a module,look for a module specification within the data. One of the forms ofdata may be another HTML file, as depicted in an illustrative example ofFIG. 6. In this example, amongst other codes of an HTML document, adocument specification may be provided as shown for example in FIG. 6.This example is a simple form of a module that would depict the words,“Hello world!”, within the portion of the container to which it has beenallocated. As is shown, the document specification is contained withinanother HTML page and accordingly the file in which the documentspecification is located likely would have the suffix of .htm or .html.In another example, a computer instruction, such as “debut,” “about” orsome other instruction may be identified that provides thespecification. Thus, according to one embodiment of the presentinvention, although the document specification may comprise an XML typefile, the source of the module specification may actually be anotherform of data or file type from which the module specification may beidentified.

In addition, a repository of data may alter, modify, change, or corrupta module specification. For example, many data repositories “escape”HTML or XML content when it is stored and used as a source. Some systemmay then unescape the source code for presentation. Accordingly, if amodule specification is included in data that has been escaped, a moduleserver or specification server may detect that the code has beenescaped, determine the manner of unescaping to be used (e.g., based onthe source, based on the type of codes used or other techniques) andthen unescape the data to return it to its original form. FIG. 6(b)illustrates an example of the file of FIG. 6 after it has been escaped.In this example, the symbol “<” has been changed to “&lt;” and thesymbol “>” has been changed to “&gt;” and several other changes havebeen made.

Similarly, with other alterations or modifications to the modulespecification, the module server or specification server may detect thealteration or modification, determine how to reverse the alteration ormodification or otherwise output the module specification to itsintended form.

Illustrative Method of Module Handling

Once a module has been incorporated into a container, when the containeris opened or refreshed, a method may be performed to generate the datafrom the module for inclusion in the container. One illustrative methodof doing so may be depicted in FIG. 7 in process 700.

In block 702, a module reference may be received from the container. Forexample, the container for a user may specify a plurality of differentmodules that are to be incorporated. It may indicate those modules by areference to the location of the module. If the module is specified astype URL, then the module is located at a place potentially remote fromthe server of the container. According to one embodiment of the presentinvention, block 704 and 706 may be provided. In block 704, the statusof the remote module may be determined, for example, by an analysismodule 28. If the remote module is approved in block 706, thenprocessing may proceed to block 710. If it is not approved, then one ormore unapproved responses may be taken in block 708. In block 710, theserver associated with the remote module reference may be called and thedata received may be evaluated. According to another embodiment of thepresent invention, block 710 may involve retrieving the remote modulefrom a cache associated with the container server. In optional block712, one or more of the activities associated with block 704 may beperformed to determine whether the remote module is approved. This maybe desired because as remote modules are under the control of anotherparty, they are subject to possible change on a frequent basis.Accordingly, in between the time that a module is included into acontainer the first time and the time which it is displayed a secondtime changes may have been made to the remote module that would renderit unapproved.

In block 714, the data that has been retrieved from the remote modulereference is parsed to identify a module specification. As discussedabove, the data may comprise a file that merely includes the modulespecification and therefore step 714 is used to extract the modulespecification from the data provided. In block 716, the modulespecification is parsed to determine how to generate data and in block718, data is returned to the container whereby the container whenaccessed by a user system or other system opening the container may beable to view the contents of the remote module. The various activitiesassociated with parsing the module specification 716 are provided ingreater detail herein.

FIG. 8 depicts more details regarding the activities involved in block716. Particularly in block 802, the parsing operation may identify thecontent type specified in the module specification and take actionappropriate based upon the content type. For example, for an HTMLcontent type, the module data is resident on the server. In block 802,module preferences may be applied if available. Greater detail regardingmodule preferences and how they may be applied are provided below. Inblock 807, user preferences may be applied if available. Greater detailabout user preferences are provided in greater detail below. In block810, based upon module preferences if available, user preferences ifavailable and the content and content type of the module specification,data may be generated for delivery to the container.

According to one embodiment, the modules may be created according to aspecification. The module specification may specify elements that arerequired and those that are optional. In one embodiment, content typeand content may be required and user preferences and module preferencesoptional. Other embodiments may have no required elements.

According to one embodiment of the present invention, a module may bespecified by an XML file, placed somewhere on the Internet where it canbe found by a module server. The XML file that specifies a module maycontain instructions on how to process and render the module that inturn may then be interpreted by the module server to render the data.The XML file may contain all of the data and code for the module or itcan have references (e.g., URLs) for where to find the rest of theelements.

There may be a plurality of different types of remote modules: HTML,URL, and XSLT, for example, or a smaller list of predefined types aswell, such as HTML and URL.

For <Content type=“html”>—the body of the <Content> is html and may behosted by the host server system 10. This may be useful for modules thatincorporate JavaScript. In one embodiment, as described herein, thecontainer may embed untrusted HTML within an IFRAME for safety.Implementations may also parse the HTML content and determine that it issafe to display without a surrounding IFRAME.

For <Content type=“url”href= . . . >—the body of the <Content> may beignored, and the IFRAME src=points to the url specified in the hrefattribute. This may be a useful content type for server-side dynamiccontent generation. In one embodiment, a url type may be served in anIFRAME. This enables the container system to obtain cookies from thesite serving the data at the URL, parse user preferences correctly andother advantages.

For <Content type=“xslt”frame=yes|no href= . . . >—body of the <Content>may be an XSLT stylesheet which is applied to the content located at theURL specified in the href=attribute. Again, the default for this type ofmodule may be IFRAME presentation as one way to protect againstmalicious HTML/JavaScript.

One example HTML module is shown below: Line Explanation <?xmlversion=“1.0” standard way to start XML files encoding=“UTF-8”?><Module> indicates that this XML file contains a module for use with acontainer document <Content type=“html”><![CDATA[ indicates that thebody of the <Content section contains HTML Hello, world! the actual HTML]]></Content> end of the Content section

According to one embodiment, a module may have a content section asshown below. <Content type=“html”> <![CDATA[ . . . place where modulecreate places HTML (or other browser recognizable code) ]]> </Content>

Module preferences may be optional per-module configuration information,such as preferred sizing, title, author, and so. For example, <Module><ModulePrefs title=“Today's place on the Internet Traffic”title_url=“http://www.placeoninternet.com/stats/” height=“200”author=“Robert Smith” author_email=“rsmith@placeoninternet.com” /><Content . . . > . . . content . . . </Content> </Module>

An example table of module preference attribute <ModulePrefs . . . >names may include: Name Description title Optional string that providesthe title of the module. This title is displayed in the module title baron the user's personalized home page. title_url Optional string thatindicates where the module resides. description Optional string thatdescribes the module. author Optional string that lists the author ofthe module. author_email Optional string that provides the moduleauthor's email address. author_affiliation Optional string thatspecifies one or more affiliations for the author (e.g., Google or Joe'sModule Developer, Inc.). height Optional positive integer that specifiesthe height of the area in which the module runs. scaling Optionalboolean that specifies whether the aspect ratio (height-to-width ratio)of the module is maintained when the browser is resized. Modules thatcan automatically scale vertically may elect to set this to true, butmodules which have a fixed height should set this to false. The defaultmay be true. scrolling Optional boolean that provides a vertical and/orhorizontal scrollbars if the content exceeds the space provided. Iffalse, then the content is clipped to the height and width provided. Thedefault may be false. render_inline Optional string that indicateswhether module may be displayed inline

Also within the <ModulePrefs> preference attribute, a <MayRequire . .. > element may specify information for compatibility and may bedisplayed in the directory. This information may also be used forattribute searches of modules. It may be used to provide information orvalidated by software within the analysis module for accuracy. In oneembodiment, this attribute may be used in presenting modules in searchresults or browsing to enable users to understand what the module mayneed to operate in the way the module creator intended.

For example, one module that requires QuickTime, a WINDOWS platform anda Firefox browser may provide the following module preference attributevalues. <ModulePrefs . . . > <MayRequire type=“plugin” value=“quicktime”/> <MayRequire type=“browser” value =“firefox” min_version=“1.06” /><MayRequire type=“platform” value=“windows” /> this is a detailedexplanation of windows </MayRequire> </ModulePrefs>

Predefined values for type and value attributes may be specified, whichmay be updated over time to include additional possible values. Atype=other may be provided as a catch-all.

If multiple MayRequire elements are provided, a logical OR may be usedto interpret multiple attributes of the same type and a logical AND maybe used to interpret multiple attributes of a different type. Forexample, multiple browsers may be specified and the interpreterunderstands that any of the specified browsers may be used. If a browserattribute and a plugin attribute are provided, the interpreterunderstands that both may be expected (the logical AND). It is alsopossible to use an attribute that specifies what a module will notoperate with.

Also within the <ModulePrefs> attribute, a <Locale . . . > element mayallow a developer to specify a country and/or language for which themodule is designed. It may be specified as <Locale lang=“ . . .”country=“ . . . ”>. Semantically, this may be interpreted to indicatethat the module is acceptable for users who have specified that theyprefer this language and/or are located in the specified country. Thismay assist a container server in complying with legal restrictions. Forexample, if a country precludes certain types of information from beingoffered for sale, a sale module may detect the locale preference topresent those items for sale only in countries where it is legal. It mayalso be used for directories and searches to hide or rank modules basedon user detected or specified locale. In addition, it may be possible toprovide an optional attribute for a code, which may allow specificationof a standardized code, such as an ISO 3166 code. In this variation,specification of such a specific code may override language and countryattributes if present.

Providing values for “lang” and “country” values may be optional. If oneis missing, it may be interpreted as an ALL value (i.e., all languagesfor a specified country or all countries for a specified language).

In one embodiment, if no locale data is specified, then the interpretermay assume one country and language (e.g., US and English) or apredefined set of countries and languages. Shorthand values may be usedas well, such as known two-digit values for countries (e.g., NZ for NewZealand, MX for Mexico, etc.). The list of countries may also bedetermined, such as by scanning content for certain words, strings,characters, etc. that are characteristic of certain locales, looking atthe author information or other possible choices. Shorthand values maybe used as well, such as known ISO two-character representations ofcountries (e.g., NZ for New Zealand, MX for Mexico, etc.).

The reader_inline attribute may be an optional preference. In oneembodiment, predetermined values may be provided including “required”which means the module must be inlined to work properly; “never” whichmeans the module will not work properly if inlined, and “optional” whichmeans it will work either way.

In other embodiments, it may be desirable to cache module specificationsthat would ordinarily be available from a specification server remotelylocated over a network from the module server. For example, if aspecification server is operating on a slower connection itstransmission of the module specification may cause the generation ofdata for the container document to be slow or unavailable.

Thus, a caching element in the module preferences may set one or moreattributes that indicates the caching rule to be applied. For example,for modules of url type, a cache rule preference may specify attributesincluding a size element (e.g., cache the module content only when thescreen size is identical, otherwise reload). This may be a defaultcaching behavior for modules that do not want the user identification tobe specified. Another attribute may be based on a “user” value (e.g.,cache the content per-user only, for any rendering dimensions). Anotherattribute may be based on a “user,size” value combination (e.g., cachethe content for a given user and given screen dimensions only). This maybe the default caching behavior for modules of a url type and thataccept a user identification. Also, an age attribute may be specifiedsuch that modules may be cached for a certain period of time. The valueof this attribute may be the maximum number of seconds to cache thecontent. This number may be suffixed with “s” for seconds, “m” forminutes, “h” for hours or “d” for days. For example, <ModulePrefsCacheMaxAge=45 d> would allow caching for 45 days. For example<ModulePrefs CacheMaxAge=0> effectively disables caching. The defaultvalue may be infinity, which can be explicitly specified with“CacheMaxAge=infinite.”

Modules may comprise “small” versions of applications suitable forcontainers such as personalized home page(s), HTML emails, portabledigital devices (PDA's), telephones, cell-phones, interactive mediadevices, video game consoles, television overlays, etc. or any otherdevice configured to display content based on a format (e.g., HTML).With a small screen size, the application may be adapted to be moreconcise and less cluttered with promotions and ads, etc. Sizing may beachieved through module preferences, with different output deviceshaving different preferences, for example or the module specifying howto behave on different output devices that render the data for display.

For example, to fit a module to the size of the window it is given, themodule may specify a height (in pixels) using <ModulePrefs . . .height=“200”>. Also, if a module does not fit in the size provided,scrollbars may be automatically added if <ModulePrefs . . . scrolling“true”>.

Module preferences may thus be used to enable module creators to specifyscreen dimensions, visibility state—e.g., full, minimized-titlebar-only,minimized-visible (e.g., visible icon on bottom or in a toolbar),minimized-invisible (e.g. only available from a menu) or closed. In allvisibility states, the module may be still “on” the user's page in thesense of able to response to events (including timed events) and able tointeract with the system (e.g. including changing its state). Also, thesystem, end user or module may control the visibility of the module,either the “default” visibility, or the visibility under a variety ofcircumstances, e.g. define states such as “active.” Illustrativeexamples include a weather module that remains minimized (for somedefinition) until there is unusual or extreme weather. A traffic modulecould remain minimized until a relevant traffic alert occurs. A stockmodule may display only stocks with changes greater than a predeterminedpercentage. A fantasy football module may be only active on weekends orwithin a predetermined period of time of the first game. The user mayhave the option to manually override these preferences from a menu, forexample. Also, as another example, an email module may size itself toreflect emails deemed important by some criteria.

Many modules may elect to access large databases and dynamic serviceshosted elsewhere on the Internet. For security purposes, browserstypically require that any JavaScript “come from” (<script src= . . . >)the same host as the content it retrieves. Therefore, a module usingsuch a technique may co-locate the JavaScript source files and theservices the JavaScript code accesses. For example, here is a workingGoogle Maps module, which uses the Maps API: <Module> <ModulePrefstitle=”Map of_(——)UP_loc_(——)” height=”300” author=”John Doe”author_email=”jdoe@emailaddresse.com” /> <UserPref name=”loc”display_name=”Location” datatype=”location” required=”true” /> -<Content type=”html”> - <![CDATA[ <scriptsrc=”http://maps.google.com/maps?file=js”type=”text/javascript”></script> <div id=”map” style=”width: 100%;height: 100%;”></div> <script type=”text/javascript”> var prefs = new_IG_Prefs(_(——)MODULE_ID_(——)); var map = newGMap(document.getElementById(“map”)); map.addControl(newGSmallMapControl( )); map.addControl(new GMapTypeControl( ));//alert(prefs.getString(“loc.lat”) + ” ”+ prefs.getString(“loc.long”));map.centerAndZoom(new GPoint(prefs.getString(“loc.long”),prefs.getString(“loc.lat”)), 6); </script> ]]> </Content> </Module>

In connection with this example, a userpref datatype=location shouldgeocode (i.e., turn a string into latitude and longitude).

Many modules may accept user preference information—for example, aweather module may expect to receive the postal code(s) the user wantsto watch. An example module with user preferences expected is shownbelow. <?xml version=”1.0” encoding=”UTF-8” ?> <Module> <ModulePrefstitle=”Weather Map” title_url= “http://www.internetplace.com/weather-map.html” height=”260” /> <UserPref name=”loc” display_name=”Location”datatype=”location” /> <Content type=”url”href=”http://www.internetplace.com/weather-map.html /> </Module>

If either the user changes the module URL, or the module specificationchanges, any previous user values may get out-of-sync with the newmodule spec. To resolve this, the server may choose to pass preferencevalues anyway. Old user preferences may be deleted, ignored or alsopassed along where the specification server may ignore them.

An example table of user preference attribute names includes thefollowing: Name Description name “Symbolic” name of the field; displayedto the end user during editing if no display_name is defined. In oneembodiment, the name field may use only letters, number and underscores,i.e. the regular expression {circumflex over ( )}[a-zA-Z0-9_]+$. Inother embodiments, other designators may also be used. display_nameOptional string to display alongside the user prefs in the edit windowurlparam Optional string name to pass as the param name for contenttype=url datatype Optional string type name (defaults to “string”) thatindicates the data type of this field. The options may include “string,”“bool” and “enum” required Optional boolean argument (“true” or “false”)indicating whether this user pref is required. default_value Optionalstring value to provide as this user pref's default value. num_minvalOptional numeric value that indicates the minimum allowed value for thisuser pref. num_maxval Optional numeric value that indicates the maximumallowed value for this user pref. cdata Repeated string value, in whicheach string is HTML. It may represent the optional data betweenpreference tags. str_maxlen Optional numeric value that specifies amaximum string length for this user pref.

Among these preferences, some modules may have logins and otherauthentications to obtain the data. This information may be passed tothe specification server through the preferences. Other techniques mayalso be used to facilitate these systems, including creating specialuser preferences for certain module creators, anonymous useridentifications passed to the specification server, placing cookies inan IFRAME for the specification server, per-user login screens and othersuch techniques.

A JavaScript preferences interface may be included with aJavaScript-based module to obtain user preference passed in. Thisinterface may comprise a plurality of JavaScript functions including thefollowing: Name Description _Container_Prefs(moduleId) The preferenceconstructor. It takes a module ID as an argument. E.g.: var prefs = new_Container_Prefs(MODULE_ID); getString(name) Retrieve the userpreference identified by name as a String value. getInt(name) Retrievethe user preference identified by name as an Integer value.getBool(name) Retrieve the user preference identified by name as aBoolean value. getModuleHeight( ) Retrieve the current module height inpixels. getModuleWidth( ) Retrieve the current module width in pixels.getUserId( ) Retrieves a unique userId for the user. dump( ) Fordebugging, uses document.writeln( ) to display all of the availablepreferences.

In addition, information related to preference protocols may be used aswell. For example, container preferences, module preferences, userpreferences, syndication recipient system preferences and users of thesyndication recipient system may specify preferences that might apply toa module. A protocol may be established that determines whichpreferences take precedence over others if a conflict exists. Forexample, if a container limits a module to 100×120 pixels and a modulepreference indicates that the module should be larger than that, thecontainer preference may override the module preference. Or, ifdifferent time zones apply to the container, the user system and thesyndication server, the time zone of the syndication server mightoverride a user preference. Other protocols are also possible.

The content section in the remote module XML file contains informationabout the module's content type. For example: <Module> <ModulePrefs . .. /> <Content type=“url” href=“http://www.placeontheinternet.com/cgi-bin/asah/modules/igstats.cgi” /> </Module> JavaScript example: <Module><ModulePrefs . . . /> <Content type=“html”> <![CDATA[ <scriptlanguage=“JavaScript”src=“http://www.placeontheinternet.com/igoogle/modules/clock/clock.js”></script> ]]> </Content> </Module>

The content section can also contain pure HTML. An example table ofmodule preference attribute names is shown below: Name Description typeOptional string that gives the type of the content. The possible valuesmay be “html,” “javascript,” “xslt,” and “url” for example. The defaultis “html.” href Optional string that provides a destination URL. Thedefault value is “”. cdata Optional string that indicates that the datageneration portion of the specification follows.

Many modules may be CGI-based front-ends to other services. To set up aCGI script, the user may create a directory, copy an example CGI scriptinto it, and test the CGI script.

Scalable Vector Graphics objects (e.g., Macromedia FLASH, MPEG4, etc.),video players, audio players, and the like may be part of a module bywrapping the code for the object with HTML that refers to and invokesit. The module server may check for this information and determine amodule to be untrusted based on inclusion of a flash object and thusserve it in an IFRAME. It is also possible that such modules may bedeemed safe and rendered inline.

Module creators may update modules. Accordingly, the module creator mayhave several options for users to learn about and/or begin using thenewer version of a module. For example, the module creator may provide anew version of a module in the same location, thus forcing users toupgrade to the new version when the container includes a reference tothat location. When a call is made to retrieve a module specification atthat location reference, the specification of the new version may beretrieved. If a module creator and/or user does not want to have newversions mandatory for the users, then a new version may be madeavailable at a different location reference in the Module Prefs. Usersmay then be notified through various mechanisms that a new version isavailable and provide them with the new location reference (e.g., URL)to use in identifying the newer version of the module in a containerdocument. For example, the module creator may publish to a new versionto a new reference locator (e.g., URL), then modify the old locationreference (e.g., URL) to provide notice to users of the upgrade.

In addition, in various embodiments, the module specification mayinclude a field or a preference that enables a module creator toindicate that a new version of the module has been created. The moduleserver may then identify an indication that a new version is availableduring the parsing process and modify the module data output (e.g.,annotating the module titlebar with an indication such as “upgradeavailable,” with a link to a confirmation window, which uponconfirmation updates the user's module location reference in thecontainer document to the newer version). For illustrative purposes,module 105 in FIG. 2 includes a selection “upgrade available” 105 a.Other methods of modifying the module data output to notify and/oraccept input related to a user selection to upgrade to the newer versionmay also be possible based upon the inclusion of information in themodule specification. In addition, it may be possible to provide aselection to enable the user to return to a previous version. Forexample, some users may not like an upgrade or the upgrade may haveperformance issues (e.g., bugs, etc.). Thus, the module server mayautomatically (or based on an input in a module specification) presentan option to a user to return to a previous version. For illustrativepurposes, module 106 has been provided with an “undo upgrade” selection106 a. This may be done for a predetermined period of time, untilanother upgrade is available or indefinitely. Indeed, repetitiveselection of “undo upgrade” may return the selection to several versionsearlier of a module.

Information related to location references of earlier versions may thenbe stored and accessible to the module server and/or be stored in themodule specification to enable those location references to be used.

In various embodiments, specification server 16 may thus run a local webserver (e.g., Apache server) or use a managed hosting facility whichtypically provides faster connection responses. By default, modulecontent may be presented in an IFRAME hosted on a domain separate fromthe domain of the container server. For example, the IFRAME may behosted by the same or different container server but served from adifferent host name (or IP address) in the URL. This may help protectusers from malicious modules that might (for example) attempt to “steal”any cookies associated with the domain of the container server.

A host server system may not want to include untrusted HTML inlinewithout precautions. A malicious module if rendered inline may read ormodify cookies, including authentication credentials, set by the hostserver system. The malicious module may also read or modify thecontainer (e.g., personalized homepage associated with the host serversystem). It may also utilize phishing (e.g., imitating a login box) orcode that replaces the entire page (via document.location) with aphishing site that looks like the personalized homepage. It may alsoutilize undesired pop-ups, dialog boxes or infinite looping codes. Amalicious module could also pass information to IFRAMEs, which may thengenerate any of the foregoing problems in the IFRAME.

Thus, according to various embodiments, the content may be placed inIFRAMEs. As an additional level of security, the content in the IFRAMEmay be served on numeric IP addresses.

Another level of protection may involve HTML type modules utilizing alibrary of scripts that hide user preferences from being generated inthe output HTML in the container.

In addition to use of IFRAMEs to render data of modules, other securityfeatures may be utilized. For example, users of the container page maybe requested to acknowledge risks when adding untrusted modules to thecontainer page. Also, untrusted models may be indicated in some manner(e.g., visual demarcation, such as a colored border). In addition,various functions may be disabled in the IFRAME, such as the JavaScriptalert( ), confirm( ), and prompt( ) functions, which may beaccomplished, in one embodiment by inserting dummy function definitions(e.g. function alert( ) {;}) before the actual content. Because anadditional IFRAME in the content could be used to circumvent thisdisabling, the container may refuse to include a module that includes anIFRAME or uses the JavaScript eval( ) function.

Illustrative Inline Generation Process

According to various embodiments of the present invention, it may bedesired to present the content of a module inline of the container.There are risks associated with inlining content into the container asdiscussed herein. Accordingly, it may be desired to enable a module tobecome inlined a container upon becoming “trusted” by the system.

A module may be deemed trusted according to various techniques includingif the module uses HTML and other codes that have been statically provento be safe through various known techniques.

Another method of achieving sufficient level of trust for the systemmight involve a methodology based upon digital signatures. Oneillustrative example methodology may be depicted in FIG. 9. This process900 may involve a number of one or more blocks. In block 902, a digitalsignature may be created. Various functions and techniques for creatingdigital signals are known and may be used herein. One such system takesvarious data as an input and randomly generates based upon those input aseries of numbers that are unique for the particular purpose (i.e., notwo people have the same digital signature).

The digital signature may be provided by the container server and/orhost server system based on a validation of the module. In oneembodiment, content of a module may be validated only if it does notinclude any external content such as IFRAMEs or javascript “src=”statements. In validating or certifying a module, it may be manuallyinspected by a person associated with the container server and/or hostserver system or a person approved by those operators.

In block 904, the creator of a module may incorporate that digitalsignal into the module. In block 906, the creator of the module mayupdate that module design specification with code that indicates thatthe module supports inline generation. When this occurs, the module whenrendered by the container server is presented inline with the container.

To avoid conflicts with other instances of the module on the user'sscreen, _MODULE_ID_ may be added to all HTML names/IDs and to allJavaScript functions and global variables. For example, varmyvariable=5; becomes var myvariable_MODULE_ID_(—)=5;. At runtime, all_MODULE_ID_ strings in the module content are replaced at runtime with aunique id for that module, even for untrusted modules.

User preferences may be accessed from an IFRAMEd or inlined module usinga preferences interface described below. <script> // May be constructedusing the _(——)MODULE_ID_(——) token. It may // get replaced at runtimewith the actual ID of the remote module. var prefs = new_Container_Prefs(_(——)MODULE_ID _(——)); var someStringPref =prefs.getString(“StringPrefName”); var someIntPref =prefs.getInt(“IntPrefName”); var someBoolPref =prefs.getBool(“BoolPrefName”); </script>

To allow both inlined and IFRAMEd modules to use the same interface toget their container dimensions (for resize events), both may be placedin an artificial <div>.

Illustrative Preference Storage

According to another embodiment of the present invention one of theelements of data stored in databases 20 may comprise preferences. Inparticular, for each user of the system that has a personalizedcontainer document, preferences may be stored. In addition, preferencesmay be stored in association with one or more modules in thepersonalized container of the user. According to one embodiment, thesystem may allocate a large volume of storage for preferences for users.

FIG. 10 illustrates an example of preferences for two users. In thisexample, one user, Bob Brown, which may be a username rather than a realname, has three modules designated for inclusion in his container. Eachmodule may be identified by an identifier (e.g., a numeric identifier orindex to a database where the data is stored) and a location reference.In this instance, the location reference is a URL of an XML file locatedat a website on the Internet. In addition, for this particular module,various preferences may be stored. In this instance, the preferenceshave been stored as follows: his name which equals Bob, his favoritecolor which equals blue, and his favorite sandwich which equals reuben.These preferences may be stored based upon the module specification forthe module at www.smith.com. Specifically, the smith.com module mayspecify that preferences may include the name, address, and age. In oneembodiment, only the preferences specified in the module specificationmay be stored in the preferences database. In another embodiment, allpreferences that the user has provided may be stored in association withthis module entry in the preferences database. For example, if theSmith.com module specification only calls for name and color preferenceinformation but used to also call for sandwich information, it ispossible that the preference entry for this module may save the ageinformation. When that information is passed to the module, the modulemay simply ignore that preference information because it is not used bythe module. Also the system may track the preferences associated withthe module and delete any preferences that have been stored inassociation with that module from the preference database that are nolonger relevant.

As FIG. 10 illustrates, entries may be provided for each user thataccesses the system to receive a personalized container. In addition,whereas this FIG. 10 illustrates that the preferences may be duplicatedfor each module (e.g., name equals Bob is stored in association witheach of the three modules for Mr. Bob Brown) it is also possible thatpreferences may be stored in a global table associated with the userwith references made to the modules to which they apply. Any othertechniques for storing preferences in association with the variousmodules to be included in the container for the user may also be usedwithin the scope of the present invention.

According to one embodiment, another security feature may be implementedwith relationship to preference storage. In particular, becausepreference values for users may be stored for various modules, it isimportant that one module not be able to modify preferences to be usedfor other modules, unless that is desired by the users and/or modulecreators (e.g., two modules that operate together, such as a maps moduleand weather module that show a weather map imposed on a street map basedon a commonly supplied user zip code preference).

Accordingly, to set preferences, in one embodiment, the module servermay include a token in the IFRAME or code of a module in HTML. For aninline system, the token may comprise a digital signature since themodule and user may already have been deemed to be trusted. Inlinedmodules may then modify other modules, the container or itself.

For IFRAMEs that may be provided on less trusted modules, the IFRAME maybe served on a numeric IP address without cookies associated with thecontainer server and any associated credentials that may be included inthe cookies (in contrast to an inline presentation where any cookies setby the container are accessible to the module running inline on thatpage, including cookies that might include a container useridentification and/or module identification).

Thus, for an IFRAME presented module, a token may be generated thatincludes information about the container and/or module and/or user.Thus, the IFRAME may be provided with a module identification (e.g., theindex of the module being displayed) and/or a container useridentification (which may be encrypted).

A token may be passed to the IFRAME and the module may then be expectedto pass back that token with any request to modify, add or removepreferences. The token may be generated according to known tokentechniques, but one illustrative example is calculated as follows: HereK1 and K2 may be secret alphanumeric characters to the server.Data=Encrypt_(K1)(Compress(ContainerUserId+ModuleId+Timestamp))Signature=HMAC_(K2)(Data+ModuleUrl)Token=Data+Signature

When a request to modify, add or remove a preference is received, themodule server may decrypt the data, validate that the timestamp iswithin a predetermined period of time of issuance (e.g., 15 minutes),look up the container user identification and module identification,calculate the signature and encrypted data and then use the moduleidentification to update the preferences if everything matches and allrequested update parameters refer to the correct module identification.A module identification may be generated for each version of a module aswell. Thus, the module location reference may not be passed in thetoken, but may be used in the calculation to generate the encryption(e.g., HMAC encryption).

The timestamp may be used to provide additional security. It may serveto limit the damage that could be done if an unauthorized user was ableto decode the token on a particular instance. Everything in the tokenmay be encrypted for additional safety, although lesser levels ofsecurity may also be used.

For example, JavaScript in a module may be created to programmaticallystore preference information for the user/module through use of thetoken system. Such a module may, with a valid token (e.g., within thetime stamp range accepted), pass data to the preference storage withoutthe user having to indicate. For example, a module that provides tasksfor a user may automatically upload newly added tasks to the preferencestorage upon entry of the new task through the module. The task listthen may be stored at the preference storage.

According to another illustrative example, preference information may beused to generate data from one or more remote modules and thatinformation may then be supplied to another remote module. For example,preference information related to one or more geographic locations maybe stored. Those one or more geographic locations may be provided toremote modules to generate information that may be supplied to mapserver 39. Map server 39 may then generate a map overlayed with databased on the geographic location information, including locations ofplaces, images of places and the like. Also, map server 39 may obtainthis information and provide it to another remote module that maygenerate mapping output or other output.

In one specific example, a string such as San Francisco, Calif. may beprovided in preference information. That string may be converted to ageocode location using geocode server 37 and passed to a remote module.The geocode location may comprise a latitude and longitude value. Theremote module may generate data for a map server to display a world maphighlighting San Francisco, Calif. on the map. If other preferenceinformation, such as “restaurants”, is provided, then restaurantlocations near San Francisco may be shown on the map. Many otherexamples are certainly possible within the scope of the presentinvention.

Illustrative Proxy Server Collection System

According to another embodiment of the present invention, throughutilizing a module that is incorporated into a container document amethod for collecting data from a target site and reformatting it in amanner desired for display by the user may be realized. For example,suppose a user is an avid fan of golf and frequents a golf websiteregularly. But the golfer is only interested in articles and informationabout how to play golf and not about events related to the PGA tour andother professional golfing events. A module may be designed with ascript that collects data from the golf site applying code that modifiesand manipulates the data collected from the golf website to generate thedata for presentation in the container. The code used by the module tocollect the data from the golf website may be viewed by the golf websiteas a robot or other unapproved access method. This may be trueparticularly if the request would have been originated from a sourcethat is unfamiliar to the golf website. For example, if the creator ofsuch a module were a unknown operator of a website, this request may beblocked or otherwise precluded by the golf website.

The operator of the host server system may be a known entity to theindividual golf site or to the community at large. Accordingly, requestsfor data from this site would not ordinarily be precluded. To utilizethe trust associated with the container site a proxy server may be usedto act on behalf of the module creator system to request the informationfrom the golf site (e.g., the target collection site) by using a serverassociated with the host server system (the proxy server address). Theinformation from the golf site may then be received by the modulecreator system, manipulated into a format desired by that modulecreator, e.g., removing all articles on a page related to the PGAtournament, highlighting information about amateur golfing, replacingnames of terms in the text to suit the module creator (replacing 7 ironfor mashie niblik), rearranging the content in the page to suit themodule creator or any other modification, replacement, substitution,deletion, addition or action the module creator wants to apply to thedata from the target collection site.

One illustrative embodiment of such a system is depicted in FIG. 11.FIG. 11 should be understood in relation to FIG. 1 in that the placementand relationship between elements as described in relation to FIG. 1should apply to FIG. 11 as well. As shown in FIG. 11, a proxy server 52may be provided that may operate in conjunction with module server 32and container server 12.

A specification server 24 may operate as the module creator system 54 aswell. In addition, a target content server 56 is depicted. As discussedabove, in one embodiment, a module specification may be stored in aplace accessible to specification server 24. When a container is openedby container server 12, a target collection module may be identified.Module server 32 may then be called to provide the data for the module.Module server 32 may determine that the specification server is locatedat a location of specification server 24 on the network. The code forthe target collection module may be retrieved by module server 32 fromspecification server 24. That code may then be delivered to containerserver 12 to display to the user. User system 22 may open the moduleand, based on code in the module data, transmit a request for data fromproxy server 52 to retrieve data from target content server 56. The datafrom target content server 56 may be provided to proxy server 52 andthen provided to the user system, where additional code in the modulemay modify and/or manipulate that data based on the code in the module.Any modifications or manipulation to that data may occur atspecification server 24 and then the data may be provided to moduleserver 32 to provide to container server 12 to generate data to theuser.

To avoid the proxy being used as an open proxy, which many systems onthe Internet disfavor, proxy server 52 and the browser systems mayemploy an authentication technique, such as the use of a token, asdescribed above related to updating preferences. Proxy server 52 mayperform requests when a specified and valid token is passed from theuser system, because it was part of the module code provided to the usersystem. In addition, caching both on the proxy server and the usersystem may be used to expedite delivery of data and reduce the number ofcalls made to the target site server.

It should be appreciated that proxy server 52 may also connect to othersystems over the Internet. In one embodiment, proxy server 52 mayutilize an address associated with and/or approved or authorized orcertified by host server system 10 to leverage the reputation of hostserver system 10 so that target content server 56 may respond with data.

An illustrative proxy method 1200 is depicted in FIG. 12. In block 1202,a container document may be opened. In block 1204, a module may beidentified that includes code to collect data from a target site. Inblock 1206, module content is transmitted in HTML to user by moduleserver 32. In block 1208, a user system (e.g., a browser) interprets theHTML including the code (e.g., the JavaScript to collect and manipulatedata) to collect data from the target collection site. In block 1210,the user system passes a request for collection of target site data tothe proxy server. It should be noted that many browsers will not act onscripting language (e.g., JavaScript) that calls a server that isdifferent from the server that sends the underlying HTML. Thus, becausethe proxy server and container server may be associated with a commonsource, the browser proceeds with the request.

In block 1212, the proxy server collects data from the target site andtransmits it to the user system. According to one illustrativeembodiment, a program referred to as trawler may be used to collect datafrom the target site. Such a service typically respects the so-calledrobot exclusion information and host load issues, similar to techniquesused to cache web page data used by web search engines. In block 1214,the user system manipulates data collected from the target site based oncode in the module specification and generates display data based on themanipulated target site data. In block 1216, the user system displays acontainer document with manipulated (optional—the data could be thetarget site data without manipulation) target site data in formatspecified by the module.

According to another embodiment, proxy server 52 may be operativelyconnected or include an analysis module 26 that performs thefunctionality described above in the context of proxy requests. Forexample, proxy server 52 and analysis module 26 may analyze requestsagainst a list of disapproved sites, disapproved actions, disapprovedcontent, etc. In addition, the requests may be compared against approvedsite, actions, contents. The evaluation may be based on the locationreference (e.g., URL) or the target site, the format of the request, thepreference values to be provided to the target site, time, userinformation, module specification source, requesting system or any otherinput.

According to other embodiments, the module specification may provideinstructions that may control the proxy server. Proxy server 52 may usethose instructions for operation. One instruction may indicate how theproxy server should obtain the data from a target site, such as byserving a fresh copy rather than using a cached version. Anotherinstruction may control the cache and its operation, includingindicating when the clean the cache or update the cache.

According to another embodiment, the target sites may be able to controlthe proxy server operations or at least provide indications as to how itwould prefer that the proxy server operate. A robot exclusion file(e.g., robots.txt) may be included indicating how proxy server mayoperate or that the proxy server may not collect data at all. Proxyserver 52 may respect instructions provided by the target site. Megatags may also be provided by the target sites. Other manners ofproviding instructions may also be provided.

The instructions provided may indicate to proxy server 52 a number ofthings, including a refresh rate, attributes as to when or for whomproxy server 52 may collect content (e.g., a list of users, modulespecifications (by URL or otherwise denoted), types of data to becollected, etc.).

According to various embodiments, the modification to the data mayinclude taking data from multiple target site sources to merge resultsinto a module output. For example, a module may take a data feed from anews source and merge it with content from a blog into a single output.Examples may include formatting, transforming and/or reformattingRSS/Atom data feeds into an HTML output; collecting webpage HTML tocreate a module, e.g., for prototyping, “mashing up” content frommultiple web pages and/or data feeds, applying internationalization tocontent, transcoding content, cleaning up “busy” content for easierpresentation, including multimedia content with other forms and thelike. Specific illustrative examples might include taking a RSS feedfrom a newspaper source, changing the font and adding the newspaper'slogo; bolding headlines that mention a specific key word or phrase,including a fictional article periodically, turn place-names intomouse-over maps in data feeds, take data from a relatively active website and create a module that contains essential links and/or featuresthat a user selects and many more.

One illustrative example of a container document that includes datagenerated through modification of proxy data is depicted in FIG. 13.There, a horoscope module is included in the container document thatincludes data collected from a horoscope RSS and then modified with textspecific to the user. Another proxy server example is depicted in the“news” module in which news, weather and maps may be included. Here,text from a news source has been collected with the term “George Bush”highlighted in the resulting information collected.

Through the use of a proxy server and/or process as described, variousadvantages may be realized. The modules may be generated for users in away that it is readily usable by user systems, such as browsers, withouta download being required (although a download of software is certainlypossible within the scope of the present invention). Users may be ableto discovery content through distribution of modules that incorporatethem and promotion of them on various locations. Creating a module usingproxy techniques may be readily done through a set of tools that thesystem may publish. Further, providing a scalable back-end server forproxying and storing user preferences also provides users with thebenefits of these modules.

OTHER ILLUSTRATIVE EXAMPLES

Accordingly, various embodiments of the present invention enable thirdparties to a host server system to create modules that are used oncontainers served by one or more host server systems or syndicated byone or more host server systems. These modules are created according toa specification that may be easy to understand and apply. Complexmodules may be possible, e.g., https, authentication, support forresizing, access to built-in libraries, etc. and remote content creatorsmay be able to develop and debug modules without downloading or learninga software development kit (SDK). In some embodiments, a standardizedplatform, such as XML, may be used and thus, the actual code used may beany that may be interpreted by the user systems that eventually willdisplay data related to the module. For example, support for JavaScriptand other languages, including more and richer libraries, documentationand example modules, and better debugging facilities may be provided.

For example, code may be generated for modules that performs customrendering for RSS/Atom feeds. RSS/Atom is a technique to publishread-only content to the web, and many modules used on container pagesare often read-only with links to pages offering richer interactivity.Moreover, host server system 10 may maintain data about modules toenable reporting on their use. This may include information about eachindividual use of the module, history of the module, modifications tothe module, syndication of the module, accounting information related tomonetary values and agreements related to the module and many othertypes of information that may be useful for reporting on the module.

Additional module types may be created as well, including an XHTML typeor modules from other systems may be possible. Additional examplemodules that may be created include a module that takes RSS informationand renders it into a format for inclusion in a container, includingdata from photoblogs, for example. Other modules may include an emailreader for popular web-based email systems, such as Gmail, AOL Mail, MSNHotmail and Yahoo! Mail. A module may be created to incorporate chatdata and instant messaging data. Simple applets may be incorporated intomodules such as clocks, calculators, notepads and the like. Othermodules may be created that operate as an interface to onlinemarketplaces for buyers and sellers of goods, such as eBay, Amazon andother online marketplaces. Modules may also be created for internal datafor various entities. For example, intranet services of an entity may berendered into modules for inclusion in a container.

The use of these modules may involve users trading the URLs of modulespecs, e.g. through search engines, email, etc. In addition, aninterface may be possible that allows various features to be added to acontainer through input of a request on another page. For example, on agolf site, there may be a link or button that says “add as a module to acontainer.” The container may be specified in advance or may be inputfrom the user. That link or button would be operated based on codeincluded by the creator of the underlying page as a way to have usersinclude that content on their container, such as their personalized homepage.

In addition, an index of modules may be created through providing ofmodule information to a search system, such as when the containerdocument retrieves a module specification, it may be passed by thecontainer server to the search system.

Further, a feedback module may be provided to collect feedback,statistics, and other data regarding modules, including informationprovided by users of modules, container document providers, target siteoperators and other parties involved in the system and/or network. Thisinformation and data may be presented to users through a ranking moduleor other module. A ranking module may rank modules based on feedback,approval, use, statistics or other criteria and may include a rankingbased on user or editorial commentary.

Also, modules may be proposed based on input about the user or containerpage, including search history, keywords in documents viewed, etc. Othertechniques may be used to promote modules for syndication as well.

In another illustrative example, a module may be created that, based ona determination that it is trusted, modify the container document toallow the user to personalize certain elements of the container document(e.g., adding the user's name, image, features, logos, etc.). Anotherillustrative example module may obtain a list of other modules on thecontainer page through interaction with the container page and obtainmetadata about them, including, for example, the ability to modify themodule(s), obtain user preferences for them. A developer module may bedeveloped to inline or IFRAME other modules for testing purposes,refresh modules (e.g., flush or renew caches) and other actions.

The present disclosure is not to be limited in scope by the specificembodiments described herein. Indeed, other various embodiments of andmodifications to the present disclosure, in addition to those describedherein, will be apparent to those of ordinary skill in the art from theforegoing description and accompanying drawings. Thus, such otherembodiments and modifications are intended to fall within the scope ofthe present disclosure. Further, although the present disclosure hasbeen described herein in the context of a particular implementation in aparticular environment for a particular purpose, those of ordinary skillin the art will recognize that its usefulness is not limited thereto andthat the present disclosure may be beneficially implemented in anynumber of environments for any number of purposes. Accordingly, theclaims set forth below should be construed in view of the full breadthand spirit of the present disclosure as described herein.

1. A proxy server system comprising: a request input unit that receivesa request to collect data from a target server; a target servercollection unit that collects data from the target server; and an outputunit that transmits the data for use by a module to generate data for acontainer document.
 2. The proxy server system of claim 1 wherein therequest is received from a module server.
 3. The proxy server system ofclaim 1 wherein the request is received from a module server remote fromthe proxy server.
 4. The proxy server system of claim 1 wherein thetarget server is a remote web server.
 5. The proxy server system ofclaim 1 wherein the proxy server connects to the target server over theInternet.
 6. The proxy server system of claim 1 wherein the output unitprovides the data to a container server.
 7. The proxy server system ofclaim 6 wherein the container server provides the data to a user system.8. The proxy server system of claim 6 wherein the container server andproxy server system have related IP addresses.
 9. The proxy serversystem of claim 6 wherein the container server and proxy server systemutilize a common domain name element.
 10. The proxy server system ofclaim 6 wherein the container server and proxy server system use thesame high level domain name.
 11. The proxy server system of claim 6wherein the container server is trusted by the target server system. 12.The proxy server system of claim 11 wherein the proxy server systemproxies the trust of the container server.
 13. The proxy server systemof claim 1 wherein the module is served to the container server by amodule server.
 14. The proxy server system of claim 13 wherein themodule server is remote from the proxy server.
 15. The proxy serversystem of claim 13 wherein the module server and container server areremote from one another.
 16. The proxy server system of claim 1 whereindata from a plurality of target servers is collected.
 17. The proxyserver system of claim 16 wherein the data from a plurality of targetservers is used by a module to generate data for a container document.18. The proxy server system of claim 16 wherein the data from aplurality of target servers is blended to form content for a containerdocument.
 19. The proxy server system of claim 1 wherein the targetserver comprises an RSS feed.
 20. The proxy server system of claim 1wherein the target server comprises a website.
 21. The proxy serversystem of claim 1 wherein the target server comprises a blog.
 22. Theproxy server system of claim 1 wherein the target server comprises anATOM feed.
 23. The proxy server system of claim 1 wherein the targetserver comprises an XML syndication feed.
 24. The proxy server system ofclaim 1 wherein the target server comprises a data feed.
 25. The proxyserver system of claim 1 wherein data from the target server is modifiedprior to presentation in a container document.
 26. The proxy serversystem of claim 25 wherein an appearance attribute of data from thetarget server is modified.
 27. The proxy server system of claim 25wherein at least a portion of the data from the target server isreplaced with other data.
 28. The proxy server system of claim 25wherein data is added to the data from the target server.
 29. The proxyserver system of claim 25 wherein at least a portion of the data fromthe target server is deleted.
 30. The proxy server system of claim 1further comprising an analysis unit to analyze the request for targetcontent.
 31. The proxy server system of claim 30 wherein the analysisunit analyzes the request based on the target data location.
 32. Theproxy server system of claim 30 wherein the analysis unit analyzes thetype of request.
 33. The proxy server system of claim 30 wherein theanalysis unit analyzes the request based on predetermined values. 34.The proxy server system of claim 33 wherein the predetermined valuesindicates disapproved requests.
 35. The proxy server system of claim 1wherein the request is received from a server based on a modulespecification.
 36. The proxy server system of claim 1 wherein therequest contains one or more instructions to the proxy server regardinghow to collect the data.
 37. The proxy server system of claim 36 whereinthe one or more instructions indicate that the content should not beretrieved from a cache.
 38. The proxy server system of claim 36 whereinthe one or more instructions indicate to control a cache associated withthe target site.
 39. The proxy server system of claim 36 wherein the oneor more instructions indicate that the cache should be cleared.
 40. Theproxy server system of claim 1 wherein the target site collection unitidentifies data at the target site that controls the target sitecollection unit.
 41. The proxy server system of claim 40 wherein thedata comprises a robot exclusion instruction.
 42. The proxy serversystem of claim 40 wherein the data comprises a mega tag.
 43. The proxyserver system of claim 40 wherein the data controls a rate at which thedata is to be refreshed rather than retrieved from cache.
 44. The proxyserver system of claim 40 wherein the data indicates informationregarding users or systems that may access content from the target site.45. The proxy server system of claim 40 wherein the data indicatesinformation regarding which module specifications may access thecontent.
 46. The proxy server system of claim 45 wherein the modulespecifications that may access the content are identified based on alocation reference.
 47. A system comprising: a container server thatserves a container document to a user with one or more associatedmodules; and a proxy server system that receives a request to collectdata from a target server, collects data from the target server andtransmits the data for use by a module to generate data for a containerdocument.
 48. A method for serving content comprising: collecting datafrom a target server using an originating address that proxies anaddress accepted by the target server; and transmitting the data fromthe target server to a server for use by a module to generate data for acontainer document.
 49. A method for delivering content comprising:transmitting a request for data from a target server to a proxy server;and receiving from the proxy server data that was obtained from thetarget server.
 50. A proxy server system comprising: input means forreceiving a request to collect data from a target server; collectionmeans for collecting data from the target server; and an output unitthat transmits the data for use by a module to generate data for acontainer document.
 51. A proxy server system comprising: a requestinput unit that receives a request originated from a user browser uponopening the content of a module included in a container document thebrowser is displaying, the request specifying a target server from whichto collect data; a target server collection unit that collects data fromthe target server; and an output unit that transmits the data for use bythe module to generate data for the container document.